Collapse WORKFLOW.md 5A to a Procedure and an Evidence Rule - #1394

…e YAML Conventions (#1395)

Collapses pull requests 2, 4 and 6 of the #1311 sequence into one
change, which the maintainer
agreed to because the three touch the same surfaces and, run
sequentially, each would re-sweep what
the last swept and pay the seam cost three times.

## What it does

**#1206's two maintainer decisions, applied first**, since sections 4
and 6 and `GOVERNANCE.md` all
depend on them. D9 binds exactly as D1 through D8 do, so a style
violation is a defect and
`GOVERNANCE.md`'s target-state framing settles *when* an unswept
workflow is fixed rather than
*whether* the violation counts. An overlap resolves **by subject**
rather than by blanket
precedence, and every section 1 to 6 now has a named owner.

**Section 4's two longest items shrink to their outcomes**, D1.6 from
about 974 words and D4.5 from
about 602. Nothing is deleted: the Microsoft.Testing.Platform runner,
package floor and its
silently-green failure modes move to `dotnet-codestyle`, the
`pytest-cov` dependency and coverage
selector to `python-codestyle`, and the failed-push recovery routes to
`operational-vs-release-workflow`.

**Section 6 states only what each type adds, and carries no N/A list at
all.** All eight per-type
N/A lists are deleted rather than corrected, because such a list is
right for a single-type
repository and negates a construct a second declared type supplies,
which is the defect #1394
shipped through fifteen clean unit passes. Section 1's applicability
rule derives the N/A set
instead, so no row can take away what another row gives. Rows are added
for the seven registry
types that had none, `upstream-wrapper` is split out of `docker`, and
the construct table keys on
the construct being present rather than on a registry field.

**`GOVERNANCE.md` "Workflow YAML Conventions" is swept** for the items
on #1367.

## What is deliberately not done

- **D6.2's publisher exception stays withdrawn.** A fourth wording was
attempted here and
disproved by `get-version-task.yml`, a called workflow whose branch
classification comes from the
caller's `GITHUB_REF` exactly as D3.1 requires. The item returns to the
text `develop` carries and
  #1369 records all four disproofs.
- **No bullet-to-D-item mapping.** One was added here, proved wrong four
ways, drifted between its
two copies in the round that wrote it, and was deleted on the
maintainer's call.
- **No per-guarantee evidence map**, per the decision recorded on #1311
step 16.
- **The `pypi` environment's deployment-branch rule is not restored**,
per the caveat #1370 records:
its one plausible content would block every `.dev0` publish D3.4
requires.

## Review evidence

21 read-only passes on the strongest tier before this pull request
existed: 11 in round one (10
whole-unit carried-content plus a cross-unit diff pass briefed to hold
`registry/repos.json` open),
9 in round two, and a terminal pair scoped to false claims and
unfollowable instructions. Roughly
220 findings, the large majority introduced by this change and disposed
of in it. The terminal pass
over `GOVERNANCE.md`, `AUDIT.md`, `CODESTYLE.md` and the four skills
returned zero.

The measurement worth recording: **the deletions were right first time
and the reasons drew nearly
everything.** Five claims about GitHub Actions behaviour that this
change introduced were falsified
by the tree and reverted, among them that `always()` and `!failure() &&
!cancelled()` are
interchangeable-with-a-preference (D1.5 *requires* `always()` for the
aggregator), and that the
registry's `releaseTrigger` decides publish-scenario applicability (it
says `two-phase` for this
repository while `publish-release.yml` is `workflow_dispatch:` only).

A carried-content pass is recorded for all 23 canonical units this
change moves.

## Owed on merge

`spec/files.json` declares both edited `GOVERNANCE.md` sections at
`verbatim` fidelity, so every
downstream copy goes stale and a fleet resync follows.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

…sh the WORKFLOW.md Reshape (#1397)

Closes #1205.
Closes #1212.
Closes #1240.
Closes #1250.
Closes #1267.
Closes #1268.
Closes #1271.
Closes #1288.
Closes #1305.
Closes #1314.

Sixteen commits, ten issues. Each was driven as its own feature pull
request into `develop`,
reviewed by the PR-hosted reviewers, and merged only with CI green and
every finding disposed of
by one of the five outcomes: fixed, declined on evidence, decided by the
maintainer, deferred
behind a filed issue, or fixed as a class.

## What this promotes

**The one-home include mechanism and its first six classes** (#1317).
`scripts/build_dist.py`
gained include regions filled from a rule's home and checked by
`--check` (#1378), so a Skill
carries a rule's whole text without a copy that can drift. Classes 2 to
6 then converted the
restatements: `agent-conduct`'s three conduct sections (#1382),
`pr-review-conduct`'s five
outcomes into `drive-pr` with every step-ref renamed to a heading
(#1383),
`backlog-burndown`'s two narrowing rows cut to the narrowing with
fourteen restatements
pointered (#1384), `WORKFLOW.md` section 4 into `workflow-ci-contract`
(#1385), and section 2
cut to a pointer at `GOVERNANCE.md` "Workflow YAML Conventions" (#1388).

**The `WORKFLOW.md` reshape** (#1311 step 14's six-pull-request
sequence, now finished). The
verdict clause aligned with section 5's Assessment (#1390), sections 3
and 5 carried into
`workflow-ci-contract` as generated includes (#1392), 5A collapsed to a
procedure and an evidence
rule (#1394), and the preamble decisions settled alongside the reshape
of section 4, section 6 and
the YAML conventions (#1395). Section 4's two longest items shrank to
their outcomes with the
displaced knowledge moved rather than deleted, and section 6 now states
only what each type adds,
carrying no N/A list at all.

**The review loop's stop rule and disposition policy** (#1330),
rewriting disposal by deletion and
committing the condition under which a whole-unit loop ends, which #1267
filed as missing.

**The Merge Gate's bound on an out-of-diff prose finding**, with the
reviewer footing recorded
(#1333), and reviewer bots scoped away from the generated Skill mirrors
(#1329) so a mirror's diff
is never reviewed in place of its source.

**The fleet label set**, declared and applied through `configure.sh`
(#1334).

**The review ledger and skills digest decoupled from the working tree**
(#1328), so concurrent
branches no longer conflict in a generated report that cannot be
hand-merged.

Plus one grouped Dependabot bump, `docker/setup-qemu-action` 4.2.0 to
4.3.0 (#1325).

## What is deliberately not closed

`#1311`, `#1317`, `#1206`, `#1367`, `#1369`, `#1370`, `#1371`, `#1386`
and `#1237` each still
hold findings this work did not settle. #1317 stands at class 6 of
fourteen, and #1311's step 17
comment records what the reshape filed rather than fixed.

## Owed on merge

`spec/files.json` declares both edited `GOVERNANCE.md` sections at
`verbatim` fidelity, so every
downstream copy goes stale on this promotion and a fleet resync follows
it.

🤖 Generated with [Claude Code](https://claude.com/claude-code)